Updating the Nodinite Web Services Monitoring Agent
The Nodinite Web Services Monitoring Agent is built on .NET and follows a monthly update release cycle with security patches, performance improvements, and bug fixes. Keep your agent up to date to maintain support and ensure compatibility with Nodinite Core Services.
On this page, you will learn how to:
- ✅ Update agents using the modern Portal-based scripted installation (v7 - recommended)
- ✅ Apply MSI-based updates to remote servers when Portal approach is not available (legacy)
- ✅ Verify compatibility and versioning for seamless upgrades
- ✅ Troubleshoot and resolve common update issues
Release notes
Visit the Release Notes for the Web Service Monitoring Agent page to review the latest features and fixes.
Important
Always read the release notes before updating to understand new features, bug fixes, and potential breaking changes.
Nodinite version 7
Preferred Method: Portal-Based Scripted Installation
In Nodinite v7, updating agents is automated through the Portal-based scripted installation. This modern approach:
✅ Automates agent installation and updates via PowerShell scripts
✅ Configures multiple agents simultaneously with consistent settings
✅ Eliminates manual MSI installations and reduces human error
✅ Centrally manages all environments from the Portal
Follow the Install Nodinite v7 or Update Nodinite v7 guide to update agents using the Portal-based approach. The Portal generates PowerShell scripts that install and configure agents automatically.
Nodinite version 6 (MSI-Based Installation - Legacy)
Warning
The MSI-based installation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted installation experience.
Running Version
View the installed version in the 'Version' text box.
Example of the run-time version information for the Web Services Monitoring Agent.
Alternatively, check the file details property on the local installation.
Example of the file version details property for the Web Services Monitoring Agent.
Compatibility and versioning issues
- 4.x -> 5.x
- Install to a new location
- Copy config and metrics files from the old installation folder to the new one
- Restart the agent and verify that everything works and metrics history is preserved
- Remove the old installation folder manually
- 4.1 -> 4.2
- Change the .NET Framework dependency from .NET 4.0 to .NET 4.5
Prerequisites for Updating
Install the Nodinite Web Services Monitoring Agent before updating. The service account must have Logon as Service Right. See Prerequisites for Web Service Monitoring Agent for more details.
Note
You must log on as a local administrator to install or update Windows Services
Update guide
Follow these steps to update the Web Services Monitoring Agent:
Step 1: Start the installer
Double-click the MSI file to start the update process for the Nodinite Web Services Monitoring Agent.
Example of the MSI installer file for the Web Services Monitoring Agent.
Step 2: Welcome Screen
When the MSI file runs, you see a Welcome screen.
Example of the Welcome screen in the Web Services Monitoring Agent installer.
Click 'Next' to continue or 'Cancel' to quit the installer.
Step 3: Custom Setup
Select features and the location to update.
Example of the Custom Setup screen showing feature and location selection.
Note
If you change the location, you will lose your old configuration
Click 'Next' to continue or 'Cancel' to quit the installer.
Step 4: Service Account Information
Enter the credentials for the Account that runs the Nodinite Web Services Monitoring Agent.
Service Account Fields
- Domain: Enter the domain name. For a local account, use the server name or a dot (.) as the domain.
- User: Enter the account name.
- Password: Enter the account password.
Example of the service account credentials dialog for the Web Services Monitoring Agent.
Note
The account must have 'Log on as Service Right'
Click 'Next' to continue or 'Cancel' to quit the installer.
Insufficient Privileges
If the account information does not meet Prerequisites for Web Service Monitoring Agent, you see an error message.
Example of the Insufficient Privileges error message during installation.
If you see this message, the account likely cannot run as a service or is not a local Administrator. Follow How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Enter valid credentials to proceed.
Tip
Check the local event log for errors (both System and Application)
Step 5: Completed setup
The last step of the update process shows either a success or a premature exit.
Example of the Completed setup screen after a successful update.
Click 'Finish' to exit the installer.
When setup finishes, your default text editor opens a file named 'README.txt'. This file provides information to help you set up and manage the agent as a Monitoring Agents for Nodinite.
Example of the README.txt file with agent setup information.
To add the Web Services Monitoring Agent as a Monitoring Agents, see the shared article below:
Troubleshooting
A failed update results in a premature exit.
Example of the premature exit screen indicating a failed update.
Support
If you cannot resolve the update problem, contact our Support.
Note
You may find additional troubleshooting information in the Windows Event Logs.
Next Step
Configuration of the agent
Related Topics
Prerequisites for Web Service Monitoring Agent
Add or manage a Monitoring Agent Configuration
Monitoring Agents
Install Web Service Monitoring Agent
Uninstall